Method and system for outputting a sequence of commands and data described by a flowchart

ABSTRACT

The present invention is a method and system for outputting a sequence of commands and data described by a flowchart. The method includes steps as follows. A flowchart describing a sequence of commands and data is received. The flowchart includes a plurality of flowchart symbols. Each of the plurality of flowchart symbols is assigned a ROM (read only memory) record. Assigned ROM records are stored in a ROM. A processor is generated to include the ROM, wherein the processor receives as input a CLOCK signal, a RESET signal, an ENABLE signal and N binary inputs x 1 , x 2 , . . . x N , and outputs the sequence of commands and data.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is a divisional application of U.S. Ser. No.11/260,517 filed Oct. 27, 2005 now U.S. Pat. No. 7,472,358. Said U.S.Ser. No. 11/260,517 is hereby incorporated by reference in its entirety.The present application further incorporates co-pending U.S. patentapplication Ser. No. 10/894,781, filed Jul. 20, 2004 by reference in itsentirety.

FIELD OF THE INVENTION

The present invention generally relates to the field of integratedcircuits, particularly to a method and system for outputting a sequenceof commands and data described by a flowchart.

BACKGROUND OF THE INVENTION

Platform-based IC (integrated circuit) design is a powerful concept forcoping with the increased pressure on time-to-market, design andmanufacturing costs encountered in the current IC market. A platform isa large-scale, high-complexity semiconductor device that includes one ormore of the following elements: (1) memory; (2) a customizable array oftransistors; (3) an IP (intellectual property) block; (4) a processor,e.g., an ESP (embedded standard product); (5) an embedded programmablelogic block; and (6) interconnect. RapidChip™ developed by LSI LogicCorp. is an instance of a platform. The basic idea behind theplatform-based design is to avoid designing and manufacturing a chipfrom scratch. Some portion of the chip's architecture is predefined fora specific type of application. Through extensive design reuse, theplatform-based design may provide faster time-to-market and reducedesign cost.

Under a platform approach, there are two distinct steps entailed increating a final end-user product: a prefabrication step and acustomization step. In a prefabrication step, a slice is built on awafer. A slice is a pre-manufactured chip in which all silicon layershave been built, leaving the metal layers or top metal layers to becompleted with the customer's unique IP. For example, RapidSlice™developed by LSI Logic Corp. is an instance of a slice. One or moreslices may be built on a single wafer. It is understood that a slice mayinclude one or more bottom metal layers or may include no metal layersat all. In a preferred embodiment of the prefabrication step, portionsof the metal layers are pre-specified to implement the pre-definedblocks of the platform and the diffusion processes are carried out in awafer fab. The base characteristics, in terms of the IP, the processors,the memory, the interconnect, the programmable logic and thecustomizable transistor array, are all pre-placed in the design andpre-diffused in the slice. However, a slice is still fully decoupledbecause the customer has not yet introduced the function into the slice.In a customization step, the customer-designed function is merged withthe pre-defined blocks and the metal layers (or late-metal components)are laid down, which couple the elements that make up the slice built inthe wafer fab, and the customizable transistor array is configured andgiven its characteristic function. In other embodiments, early-metalsteps may be part of the pre-fabricated slice to reduce the time andcost of the customization step, resulting in a platform which is morecoupled and specific. It is understood that a prefabrication step and acustomization step may be performed in different foundries. For example,a slice may be manufactured in one foundry. Later, in a customizationstep, the slice may be pulled from inventory and metalized, which givesthe slice its final product characteristics in a different foundry.

A slice such as RapidSlice™ may contain several RRAMs (ReconfigurableRAMs, or Redundant RAMs, or RapidSlice™ RAMs). Each RRAM is a set ofmemories of the same type that are placed compactly. RRAMs includebuilt-in testing and self-repairing components. The process of testingmemories of RRAMs and self-repairing these memories is managed by a RRAMcontroller, which may receive a sequence of commands and data output bya kernel of this controller, or processor. The processor is a devicethat has N binary inputs: x₁, x₂, . . . x_(N), and 2 wide outputs:command and data. The processor may produce as output a specificsequence of commands and data. These commands and data are then sent toother devices of the RRAM controller for further processing.

Under a platform approach, RRAMs, the RRAM controller, and the processorare typically pre-diffused in a slice. Since different customers may useRRAMs differently, it is thus desirable to provide a processor thatincludes as few variable components as possible. That is, it isdesirable to have a processor where the change of the sequence ofcommands and data to be output by the processor may not lead to theglobal change of the processor already diffused in the slice.

SUMMARY OF THE INVENTION

In a first exemplary aspect of the present invention, a method foroutputting a sequence of commands and data described by a flowchartincludes steps as follows. A flowchart describing a sequence of commandsand data is received. The flowchart includes a plurality of flowchartsymbols. Each of the plurality of flowchart symbols is assigned a ROM(read only memory) record. Assigned ROM records are stored in a ROM. Aprocessor is generated to include the ROM, wherein the processorreceives as input a CLOCK signal, a RESET signal, an ENABLE signal and Nbinary inputs x₁, x₂, . . . x_(N), and outputs the sequence of commandsand data.

In a further exemplary aspect of the present invention, a method forconstructing a processor for outputting a sequence of commands and datadescribed by a flowchart includes steps as follows. A processorincluding a ROM is diffused in a slice. The processor is connected to aRRAM controller in the slice. A flowchart describing a sequence ofcommands and data is received. The flowchart includes a plurality offlowchart symbols. Each of the plurality of flowchart symbols isassigned a ROM record. The ROM records are stored in the ROM. Theprocessor outputs the sequence of commands and data to the RRAMcontroller for managing a process of testing and self-repairing memoriesof RRAMs, which are communicatively coupled to the RRAM controller.

In another exemplary aspect of the present invention, a system foroutputting a sequence of commands and data described by a flowchartincludes a ROM for storing ROM records. The ROM records are assigned toflowchart symbols, which are used by a flowchart to describe or define asequence of commands and data. The system further includes a logicmodule PROCESSOR_CONTROL for receiving the ROM records from the ROM andoutputting the sequence of commands and data. The logic modulePROCESSOR_CONTROL is communicatively coupled to the ROM and includesflipflops.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory onlyand are not restrictive of the invention as claimed. The accompanyingdrawings, which are incorporated in and constitute a part of thespecification, illustrate an embodiment of the invention and togetherwith the general description, serve to explain the principles of theinvention.

BRIEF DESCRIPTION OF THE DRAWINGS

The numerous advantages of the present invention may be betterunderstood by those skilled in the art by reference to the accompanyingfigures in which:

FIG. 1 is a flow diagram showing a method for outputting a sequence ofcommands and data described by a flowchart in accordance with anexemplary embodiment of the present invention;

FIG. 2 is a simplified schematic diagram showing a system for outputtinga sequence of commands and data described by a flowchart in accordancewith an exemplary embodiment of the present invention, where the systemincludes a processor and a RRAM controller;

FIG. 3 shows an exemplary internal structure of the processor shown inFIG. 2 in accordance with an exemplary embodiment of the presentinvention; and

FIG. 4 is a flow diagram showing a method for constructing a processorfor outputting a sequence of commands and data described by a flowchartin accordance with an exemplary embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

Reference will now be made in detail to the presently preferredembodiments of the invention, examples of which are illustrated in theaccompanying drawings.

FIG. 1 is a flow diagram showing a method 100 for outputting a sequenceof commands and data described by a flowchart in accordance with anexemplary embodiment of the present invention. The method 100 may startwith step 102 in which a flowchart describing a sequence of commands anddata is received. The flowchart includes a plurality of flowchartsymbols. In a preferred embodiment, the flowchart symbols includes:command and data, jump, optional jump, start, finish, startsubflowchart, call subflowchart, and finish subflowchart. The commandand data symbol contains 2 values: command and data desired to be outputwhen this symbol is processed. The command and data symbol may also havea condition that can be of one of the following four types: if(x_(k)) orif(!x_(k)) or while(!x_(k)) or while(!x_(k)). If the command and datasymbol has a condition, then command and data are output if x_(k)=1only, if x_(k)=0 only, while x_(k)=1, or while x_(k)=0. The command anddata symbol with the condition “if” is called an optional command anddata symbol. The command and data symbol with the condition “while” iscalled a continuous command and data symbol. The command and data symbolwith no condition is called a simple command and data symbol.

The jump symbol contains the address of the flowchart symbol that needbe processed immediately after the current symbol. The optional jumpsymbol has the address of the flowchart symbol that need be processedimmediately after the current symbol if some condition is valid. Thecondition may be of one of the following two types: if (x_(k)) or if(!x_(k)). The start and finish are the symbols which mean starting andfinishing the processor work, respectively. The start symbol must be thefirst symbol of the flowchart. All of the following symbols jump,optional jump, finish, call subflowchart and finish subflowchart mayalso have 2 values: command and data that need be output when the givensymbol is being executed.

The flowchart may include some subflowcharts. Each subflowchart startswith the symbol start subflowchart and finishes with the symbol finishsubflowchart. The subflowchart may be called from any place of theflowchart and may be called from any other subflowchart. Let M be themaximal depth of the subflowchart call stack. Below is an example of aflowchart describing a sequence of commands and data:

1. start

2. command 1, data 2 if(x₁)

3. command 1, data 3

4. if (x₁) goto 8

5. if (!x₂) goto 8, command 6, data 5

6. call subflowchart1

7. call subflowchart1

8. command 8, data 8 while(x₂)

9. finish

10. start subflowchart1

11. call subflowchart2

12. call subflowchart2, command 7, data 7

13. finish subflowchart1

14. start subflowchart2

15. command 2, data 3

16. command 2, data 4

17. finish subflowchart2

The foregoing-indicated exemplary flowchart has 2 inputs: x₁ and x₂. Themaximal call stack depth M=3. If the values of inputs x₁ and x₂ are 0and 1, respectfully, then the processor described by the flowchartgenerates the following sequence of commands and data on its outputs:(1,3), (6,5), (2,3), (2,4), (7,7), (2,3), (2,4), (2,3), (2,4), (7,7),(2,3), (2,4), (8,8), (8,8), (8,8), . . . . If x₁=0 and x₂=0, then thesequence is (1,3), (6,5). If x₁=1 and x₂=0, then the sequence is (1,2),(1,3). If x₁=1 and X₂=1, then the sequence is (1,2), (1,3), (8,8),(8,8), (8,8), . . . .

The present invention may provide a method for constructing a processorfor a flowchart. The processor may be diffused on a predetermined slicesuch as RapidChip™, and the like. The processor insertion (placement,routing, etc.) into the slice is implemented only once. Thus, it isdesirable to develop a processor with as few variable parts as possible.That is, the change of the flowchart may not lead to a global change ofthe processor already diffused on the slice. The present invention mayfulfill this requirement. The variable part of the present processor isthe data stored in the special ROM (read only memory). All other partsof the present processor are constant and may, together with ROM, beinserted in the slice and be permanently connected to RRAMs and someother slice cores.

The co-pending U.S. patent application Ser. No. 10/894,781, filed Jul.20, 2004 disclosed a RapidChip™ RRAM control kernel device (CKD). Incomparison with the CKD, the present processor may make greatimprovement because of the following reasons. First, the presentprocessor supports a wider set of flowcharts than the CKD does. The CKDdoes not support optional and continuous command and data symbols andsupports simple command and data symbols only. The CKD also does notsupport outputting some commands and data while processing jump,optional jump, finish, call subflowchart, finish subflowchart symbols.Moreover, the timing characteristics of the present processor are muchbetter than the timing characteristics of the CKD built for the sameflowchart because the processor and the CKD have different architecture.The CKD may have long timing paths that go through the ROM and logicalcells of the module CKD_CONTROL. In contrast, the present processor hassome extra flipflops that break the long logical paths. Due to thisfeature the operating frequency of the present processor is up to 2times better than the operating frequency of the CKD built for the sameflowchart.

Let N be the maximal number of inputs of the flowchart, let M>=1 be themaximal depth of the subflowchart call stack, let S be the maximalnumber of symbols in the flowchart, let CS be the bit width of theoutput command, and let DS be the bit width of the output data. In oneembodiment, the present processor (see FIG. 3) includes a ROM and somelogical cells and flipflops. Denote RW to be a ROM width (or the bitsize of words stored in this ROM). The capacity (number of stored words)of this ROM is equal to S (or the maximal number of flowchart symbols).Assign RW=3+CS+DS+log₂ N+max(3,log₂ S+log₂ N). Throughout the presentinvention, the notation log₂ A represents the smallest integer numberthat is not less than log₂ A.

For each symbol denote <command_value> and <data_value> to be commandand data that need be output when the symbol is being processed, where<command_value> includes CS bits and <data_value> includes DS bits. Foreach symbol denote <input_index> as follows:

-   -   1) for symbols start, start subflowchart, simple command and        data, jump, call subflowchart, finish subflowchart and finish,        define <input_index>=00 . . . 0 (log₂ N zeroes); and    -   2) for symbols optional command and data, continuous command and        data and optional jump, define <input_index>=k₁k₂ . . .        k_(log N), where k₁k₂ . . . k_(logN), is a binary presentation        of the index “i” of the input x_(i) involved in the condition.

For each symbol denote <next_input_index> to be the <input_index> of thesymbol that follows the given symbol in the flowchart. For the lastsymbol of the flowchart, <next_input_index>=00 . . . 0 (log₂ N zeroes).

Still referring to FIG. 1, each of the plurality of flowchart symbols isexamined and assigned a ROM (read only memory) record 104. The ROMrecord may be assigned as follows:

-   -   1) for symbols start or start subflowchart:        000<command_value><data_value><next_input_index>;    -   2) for symbol simple command and data:        001<command_value><data_value><next_input_index>000;    -   3) for symbol optional command and data if(x_(i)):        001<command_value><data_value><next_input_index>001;    -   4) for symbol optional command and data if(!x_(i)):        001<command_value><data_value><next_input_index>002;    -   5) for symbol continuous command and data while(x_(i)):        001<command_value><data_value><next_input_index>003;    -   6) for symbol continuous command and data while(!x_(i)):        001<command_value><data_value><next_input_index>004;    -   7) for symbol jump:        002<command_value><data_value><next_input_index><jump_address>;    -   8) for symbol optional jump with condition if(x_(i)):        003<command_value><data_value><next_input_index><jump_address><jump_input_index>,        where the <jump_input_index> is the <input_index> of symbol to        which jump is addressed;    -   9) for symbol optional jump with condition if(!x_(i)):        004<command_value><data_value><next_input_index><jump_address><jump_input_index>,        where the <jump_input_index> is the <input_index> of symbol to        which jump is addressed;    -   10) for symbol call subflowchart:        005<command_value><data_value><next_input_index><address><jump_input_index>,        where <address> is the address of the symbol start subflowchart        of the corresponding subflowchart, and <jump_input_index> is the        <input_index> of this symbol;    -   11) for symbol finish subflowchart:        006<command_value><data_value><next_input_index>; and    -   12) for symbol finish:        002<command_value><data_value><input_index><address><input_index>,        where <address> is the address of the given flowchart symbol        finish. It means that when one reaches the finish symbol, one        stops at this symbol forever (while the signal RESET does not        appear).

Assigned ROM records are stored in a ROM (e.g. ROM 302 in FIG. 3) 106.It is possible that the ROM record assigned for a flowchart symbol mayhave a bit size that is less than a width RW of the ROM. In this case,preferably at least one zero is appended to the end of the ROM record inorder to obtain the size RW.

A processor is generated to include the ROM, wherein the processorreceives as input a CLOCK signal, a RESET signal, an ENABLE signal and Nbinary inputs x₁, x₂, . . . x_(N), and outputs the sequence of commandsand data 108. The processor (see, e.g., processor 202 in FIGS. 2 and 3)generates the sequence of commands and data described by the flowchartto a RRAM controller (see, e.g., RRAM controller 204 in FIG. 2). Theprocessor may have some additional ports: input CLOCK, input RESET, andinput ENABLE. The inputs CLOCK and RESET are the clock and reset inputsthat drive all flipflops and ROM of the processor, and the input ENABLEis used for temporarily halting the work of the processor. If ENABLE=0,then the work of the module is halted. The processor may be described ina hardware description language.

The following is a description of a processor architecture (see, e.g.,processor 202 in FIG. 3) in a hardware description language similar toVerilog:

module PROCESSOR(CLOCK, RESET, ENABLE, X, COMMAND, DATA) input CLOCK,RESET, ENABLE; input [N−1:0] X; output [CS−1:0] COMMAND; output [DS−1:0]DATA; wire [log₂S−1:0] read_rom_address; wire [RW−1:0] rom_data; ROMrom_inst (.RA(read_rom_address), .DO(rom_data)); PROCESSOR_CONTROLcontrol_inst (.ENABLE(ENABLE), .X(X), .COMMAND(COMMAND), .DATA(DATA),.rom_data(rom_data), .read_address(read_rom_address)); endmodule

As shown, the module PROCESSOR contains 2 instances: the instance“rom_inst” of the ROM and the instance “control_inst” of a logicalmodule PROCESSOR_CONTROL (e.g., PROCESSOR_CONTROL 304 in FIG. 3, whichincludes flipflops 306, 308, 310 and 312, and logics) that processes thedata “rom_data” read from the ROM and generates the “read_address”.

The logical module PROCESSOR_CONTROL may be described as follows:

module PROCESSOR_CONTROL(ENABLE, X, COMMAND, DATA, rom_data,read_address) input ENABLE; input [N−1:0] X; output [CS−1:0] COMMAND;output [DS−1:0] DATA; input [RW−1:0] rom_data; output [log₂S−1:0]read_address; wire [2:0] symbol_type; wire [CS−1:0] tmp_command; wire[DS−1:0] tmp_data; wire [log₂S−1:0] jump_address; wire [2:0]command_condition_type; wire [log₂N−1:0] next_input_index; wire[log₂N−1:0] jump_input_index; assign symbol_type = rom_data[2:0]; assigntmp_command = rom_data[CS+2 : 3]; assign tmp_data = rom_data[DS+CS+2 :CS+3]; assign command_condition_type = rom_data[DS+CS+5 : DS+CS+3];assign next_input_index = rom_data[log₂N+DS+CS+2 : DS+CS+3]; assignjump_address = rom_data[log₂S+log₂N+DS+CS+2 : log₂N+DS+CS+3];assign jump_input_index = rom_data[log₂S+2log₂N+DS+CS+2 : log₂S+log₂N+DS+CS+3]; wire valid_output; reg [log₂S−1:0] address; reg[log₂N−1:0] input_index; reg [log₂S−1:0] call_stack[M]; // array ofregisters of the length M reg [log₂N−1:0] input_index_stack[M]; // arrayof the registers of the length M wire [log₂N−1:0] current_input_index;if (ENABLE==0) {  valid_output = 0; } else { current_input_index =input_index; read_address = address+1; valid_output = 1; input_index =next_input_index; switch (symbol_type) { case 3b’000: // start or startsubflowchart break; case 3b’001: // command and data switch(command_condition_type) { case 3b’001: // optional command and dataif(x_(i)) if (X[input_index]==0) { valid_output = 0; } case 3b’002: //optional command and data if(!x_(i)) if (X[input_index]==1) {valid_output = 0; } case 3b’003: // continuous command and datawhile(x_(i)) if (X[input_index]==1) { read_address = address;input_index = current_input_index; } else { valid_output = 0; } case3b’004: // continuous command and data while(!x_(i)) if(X[input_index]==0) { read_address = address; input_index =current_input_index; } else { valid_output = 0; } break; } break; case3b’002: // jump or finish read_address = jump_address; input_index =jump_input_index; break; case 3b’003: // optional jump with conditionif(x_(i)) if (X[input_index]==1) { read_address = jump_address;input_index = jump_input_index; } break; case 3b’004: // optional jumpwith condition if(!x_(i)) if (X[input_index]==0) { read_address =jump_address; input_index = jump_input_index; } break; case 3b’005: //call subflowchart read_address = jump_address; input_index =jump_input_index; for (int i=M−1;i>=1;i−−) { call_stack[i] =call_stack[i−1]; input_index_stack[i] = input_index_stack[i−1]; }call_stack[0] = address+1; input_index_stack[0] = next_input_index;break; case 3b’006: // finish subflowchart read_address = call_stack[0];input_index = input_index_stack[0]; for (int i=1;i<M;i++) {call_stack[i−1] = call_stack[i]; input_index_stack[i−1] =input_index_stack[i]; } break; } address = read_address; } assignCOMMAND = valid_output & tmp_command; assign DATA valid_output &tmp_data; endmodule

The registers “call_stack[i]”, i=0, 1, . . . , M−1, store thesubflowchart call stack addresses. The registers “input_index_stack[i]”,i=0, 1, . . . , M−1, store the <input_indexes> of symbols with addresses“call_stack[i]”. Due to storing “input_indexes” of executed symbols inregisters (flipflops), one may achieve a significant reduction of thelength of the logical paths through ROM and PROCESSOR_CONTROL incomparison with the analogue paths of the CKD described in theco-pending U.S. patent application Ser. No. 10/894,781, filed Jul. 20,2004.

It is understood that the foregoing-indicated descriptions in thehardware description language not only describes a processorarchitecture used for a RRAM controller, but can also be used to definean architecture for a device that sends control commands and data toother devices without departing from the scope and spirit of the presentinvention.

Thus, the present invention provides a method and system for creating aprocessor based on a given flowchart defining a sequence of commands anddata. The variable part of the created processor is the data (ROMrecords) stored in the ROM, while all other parts of the processorremain constant. As a result, when the flowchart changes, only the datastored in the ROM needs to be changed. The present processor can thus bepre-diffused in a slice to provide a sequence of commands and data to aRRAM controller also pre-diffused in the same slice. When a customerwishes to change the sequence of commands and data to be output by theprocessor, the customer only needs to change the data stored in the ROMof the processor, which does not require a global change to theprocessor.

FIG. 4 is a flow diagram showing a method 400 for constructing aprocessor for outputting a sequence of commands and data described by aflowchart in accordance with an exemplary embodiment of the presentinvention. The method 400 may start with step 402 in which a processorincluding a ROM is diffused in a slice 402. The processor may have aninternal architecture shown in FIG. 3 and may be described by theforegoing hardware description language. The slice is a pre-manufacturedchip in which all silicon layers have been built, leaving the metallayers or top metal layers to be completed with the customer's uniqueIP. For example, RapidSlice™ developed by LSI Logic Corp. is an instanceof a slice. The processor is connected to a RRAM controller alsodiffused in the slice 404. A flowchart describing a sequence of commandsand data is received 406. The flowchart may be provided by a customer.The flowchart includes a plurality of flowchart symbols. Each of theplurality of flowchart symbols is assigned a ROM record 408. The ROMrecords are stored in the ROM 410. The processor outputs the sequence ofcommands and data to the RRAM controller for managing a process oftesting and self-repairing memories of RRAMs, which are communicativelycoupled to the RRAM controller 412.

It is to be noted that the foregoing described embodiments according tothe present invention may be conveniently implemented using conventionalgeneral purpose digital computers programmed according to the teachingsof the present specification, as will be apparent to those skilled inthe computer art. Appropriate software coding may readily be prepared byskilled programmers based on the teachings of the present disclosure, aswill be apparent to those skilled in the software art.

It is to be understood that the present invention may be convenientlyimplemented in forms of a software package. Such a software package maybe a computer program product which employs a computer-readable storagemedium including stored computer code which is used to program acomputer to perform the disclosed function and process of the presentinvention. The computer-readable medium may include, but is not limitedto, any type of conventional floppy disk, optical disk, CD-ROM,magneto-optical disk, ROM, RAM, EPROM, EEPROM, magnetic or optical card,or any other suitable media for storing electronic instructions.

It is understood that the specific order or hierarchy of steps in theprocesses disclosed is an example of exemplary approaches. Based upondesign preferences, it is understood that the specific order orhierarchy of steps in the processes may be rearranged while remainingwithin the scope of the present invention. The accompanying methodclaims present elements of the various steps in a sample order, and arenot meant to be limited to the specific order or hierarchy presented.

It is believed that the present invention and many of its attendantadvantages will be understood by the foregoing description. It is alsobelieved that it will be apparent that various changes may be made inthe form, construction and arrangement of the components thereof withoutdeparting from the scope and spirit of the invention or withoutsacrificing all of its material advantages. The form herein beforedescribed being merely an explanatory embodiment thereof, it is theintention of the following claims to encompass and include such changes.

1. A method for constructing a processor for outputting a sequence ofcommands and data described by a flowchart, comprising: diffusing aprocessor in a slice, said processor including a ROM; connecting saidprocessor to a RRAM controller in said slice; receiving a flowchartdescribing a sequence of commands and data, said flowchart including aplurality of flowchart symbols of an integrated circuit; assigning ROMrecords to said plurality of flowchart symbols; storing said ROM recordsin said ROM; outputting, by said processor, said sequence of commandsand data to said RRAM controller for managing a process of testing andself-repairing memories of RRAMs, said RRAMs being communicativelycoupled to said RRAM controller.
 2. A system for outputting a sequenceof commands and data described by a flowchart, comprising: a ROM forstoring ROM records, said ROM records being assigned to flowchartsymbols of an integrated circuit, said flowchart symbols being includedin a flowchart describing a sequence of commands and data; a logicmodule PROCESSOR_CONTROL, communicatively coupled to said ROM, forreceiving said ROM records from said ROM and outputting said sequence ofcommands and data, said logic module PROCESSOR_CONTROL includingflipflops, said logic module PROCESSOR_CONTROL receives as input a CLOCKsignal, a RESET signal, an ENABLE signal and N binary inputs x₁, x₂, . .. x_(N); and a RRAM controller communicatively coupled to said logicmodule.
 3. The system of claim 2, wherein the RRAM controller iscommunicatively coupled to said logic module for providing said ENABLEsignal and said N binary inputs x₁, x₂, . . . x_(N) to said logic modulePROCESSOR_CONTROL and for receiving said sequence of commands from saidlogic module PROCESSOR_CONTROL, wherein said RRAM controller manages aprocess of testing and self-repairing memories of RRAMs, said RRAMsbeing communicatively coupled to said RRAM controller.
 4. The system ofclaim 2, wherein said flowchart symbols include command and data, jump,optional jump, start, finish, start subflowchart, call subflowchart, andfinish subflowchart.
 5. The system of claim 4, wherein said ROM recordsare assigned as follows: 1) for symbols start or start subflowchart:000<command_value><data_value><next_input_index>; 2) for symbol simplecommand and data: 001<command_value><data_value><next_input_index>000;3) for symbol optional command and data if(x_(i)):001<command_value><data_value><next_input_index>001; 4) for symboloptional command and data if(!x_(i)):001<command_value><data_value><next_input_index>002; 5) for symbolcontinuous command and data while(x_(i)):001<command_value><data_value><next_input_index>003; 6) for symbolcontinuous command and data while(!x_(i)):001<command_value><data_value><next_input_index>004; 7) for symbol jump:002<command_value><data_value><next_input_index><jump_address>; 8) forsymbol optional jump with condition if(x_(i)):003<command_value><data_value><next_input_index><jump_address><jump_input_index>,where said <jump_input_index> is an <input_index> of a symbol to whichjump is addressed; 9) for symbol optional jump with conditionif(!x_(i)):004<command_value><data_value><next_input_index><jump_address><jump_input_index>,where said <jump_input_index> is an <input_index> of a symbol to whichjump is addressed; 10) for symbol call subflowchart:005<command_value><data_value><next_input_index><address><jump_input_index>,where said <address> is an address of a symbol start subflowchart of acorresponding subflowchart, and said <jump_input_index> is an<input_index> of said symbol; 11) for symbol finish subflowchart:006<command_value><data_value><next_input_index>; and 12) for symbolfinish:002<command_value><data_value><input_index><address><input_index>, where<address> is an address of said flowchart symbol finish.